Alaaddin Alaa
asked on
DNS server can't resolve it self
Hi
yesterday I notice an issue on my primary DNS server as follows:
I went to the dns server under the forward lookup zones on _msdcs.mydomain.local properties ---> name servers -----> edit on my primary dns server ------> trying to resolve its name but it shows this message .... "a timeout occurred during validation"
tried to do the same steps on my additional DC on its DNS server everything works fine.... and I don't have any problem resolving the workstations on my network
but when I do nslookup on the primary DC it shows this message if the primary DNS server set to it self
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: 192.168.10.10
note : the IPv6 is disabled
yesterday I notice an issue on my primary DNS server as follows:
I went to the dns server under the forward lookup zones on _msdcs.mydomain.local properties ---> name servers -----> edit on my primary dns server ------> trying to resolve its name but it shows this message .... "a timeout occurred during validation"
tried to do the same steps on my additional DC on its DNS server everything works fine.... and I don't have any problem resolving the workstations on my network
but when I do nslookup on the primary DC it shows this message if the primary DNS server set to it self
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: 192.168.10.10
note : the IPv6 is disabled
masnrock
On the problematic DC, go to the properties for the DNS server, and create a PTR record for that server in the reverse lookup zone. Once you do that, restart the DNS service. Let me know if you're still having issues.
ASKER
it didn't help
the nslookup output showing that PTR record for DC is missing
if you don't create that, it will not create any name resolution issues but nslookup output will not correct then
if you don't create that, it will not create any name resolution issues but nslookup output will not correct then
Check for PTR records pointing to the problematic DC on BOTH DCs then. Make sure that record exists in the reserve lookup zone.
If I understand you're asking to have both these resolutions work...
To have the second (reverse lookup work), only the person in control of the physical IP can set this record.
If you're using a full featured Provisioning company, like OVH, you can just login to your customer dashboard + set this yourself.
Usually you'll have to open a ticket with your Hosting company to do this.
If you do this in your own Zone File, your record will be quietly ignored, because the syntax is correct... it's just the record will never be looked up, because this type of record is looked up based on your upstream provider.
foo.com -> 1.1.1.1
1.1.1.1 -> foo.comTo have the second (reverse lookup work), only the person in control of the physical IP can set this record.
If you're using a full featured Provisioning company, like OVH, you can just login to your customer dashboard + set this yourself.
Usually you'll have to open a ticket with your Hosting company to do this.
If you do this in your own Zone File, your record will be quietly ignored, because the syntax is correct... it's just the record will never be looked up, because this type of record is looked up based on your upstream provider.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.