The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
DNS and Domain issues
Apothe0sis
Have you ever questioned the nature of your reality?Registered User regular
Have you ever questioned the nature of your reality?Registered User regular
Well,
I've been lucky enough to inherit what I can best describe as a spaghetti setup as my first job involving any network administration at all.
It's for a relatively small company and they;re running an SBS 2003 server as our domain controller.
For some reason, I've got two computer which steadfastly refuse to respond to their FQDN from any other computer on the network/domain.
Everything else, on the network responds nice and politely.
computer1.domain.com can be pinged, accessed and otherwise spoken to by FQDN.
computer2.domain.com can be pinged, accessed and otherwise spoken to by FQDN only but itself only. Talk to it by its regular hostname computer2 and everyone can talk to it again.
Why is it broken? I've looked in what seem to me to be all the usual suspects and trawled through everything I can find in MMC. Is the domain controller spastic or are the computer retarded?
I've been lucky enough to inherit what I can best describe as a spaghetti setup as my first job involving any network administration at all.
It's for a relatively small company and they;re running an SBS 2003 server as our domain controller.
For some reason, I've got two computer which steadfastly refuse to respond to their FQDN from any other computer on the network/domain.
Everything else, on the network responds nice and politely.
computer1.domain.com can be pinged, accessed and otherwise spoken to by FQDN.
computer2.domain.com can be pinged, accessed and otherwise spoken to by FQDN only but itself only. Talk to it by its regular hostname computer2 and everyone can talk to it again.
Why is it broken? I've looked in what seem to me to be all the usual suspects and trawled through everything I can find in MMC. Is the domain controller spastic or are the computer retarded?
Apothe0sis on
0
Posts
If the record isn't there you could enter it manually or run at the command line on computer2 "ipconfig /registerdns". I think in the TCP/IP settings on the LAN connection of computer2 you can check a box labelled "register this connection w/DNS" or somesuch, and there are some settings in DHCP that also inform how DNS records are being updated by the DHCP server.
If computer2 has multiple A records with different IPs then something wonky is happening with respect to how the IP information is getting updated in DNS. Cannot give you the proper setting/explanation right now, but this article may help.
Also thought maybe a firewall on computer2 might be interfering, unlikely if CIFS is working (access by \\computer2\) but possible that ICMP is not being permitted.
p.s. - Thanks for the tip on krdp, I had no idea. Looking to see if it will work on OSX.
There was a DNS record for some-non-existent computer which pointed to its IP. Which meant that I was trying to talk to the wrong FQDN. I have removed that record and then tried to reregister the computer with ipconfig /registerdns but nothing is happening there, no new ptrs or records are appearing and no errors are appearing in the event viewers of either teh workstation or the server.
Which probably tells me why the other computer isn't playing ball either - its attempts to register with the dns are being ignored.
Which is to say that it was but a moments work to manually create the DNS entries. However, I am curious as to why they're not doing their thing automagically.
If not check out the Window's hosts file? I know there's some sort of equivalent in Windows.
Also... wait you're using FQDN having DNS suffixes appended wouldn't matter.
I've also seen a trust issue with the computers account cause the DNS server to reject updates from that box, but that should be logged. Nada in the DNS event log?