Secondary DNS server does not give FQDN on ping -a

I set up a secondary DNS server for redundancy and used the wizard so it should have pulled the DNS settings from the current DNS server. It seems to be working fine but while troubleshooting a Blackberry issue I found if a PC/server used dns02 (the new one) as the logon server when I ping then ping -a from that device I do not get the FQDN, only the name. If I ping from a device that used dns01 as the logon server then I do get the FQDN. I have compared settings on the 2 dns servers and cannot see any difference. What should I look for?

Both servers are MS 2003 SP1
LarryDAHAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
martin_babarikConnect With a Mentor Commented:
I also think so, but just to make sure: open the DNS console, expand forward lookup zones, select your zone, right click and choose "Properties". On the first tab you will see the zone type (should see Active Directory integrated).
Do the same for your reverse lookup zone on both servers.

Regarding the records - I think that's correct the way you have it.
But one thing that might be the cause of the problem - you have only Name servers record and no Host record - you need to have this one, otherwise the name resolution will not succeed. I think when you create these, it will work.
0
 
martin_babarikCommented:
Hi, when you use "ipconfig /all" on both servers, do you see the same primary DNS suffix? If not, change it My computer -> Properties -> Computer name -> Change -> More.
Also if you want to ping by IP and get the FQDN as a result, you should create a reverse lookup zone and create PTR records there.
0
 
LarryDAHAuthor Commented:
ipconfig /all shows the same primary DNS suffix on both servers and the new server does have a reverse lookup zone and it has the same PTR records as the primary DNS server.

What else can I check?
0
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

 
martin_babarikCommented:
Thanks. Just to get a more clear idea about your network: are both servers domain controllers and is the zone AD integrated on both of them?
What is the ipconfig of both servers?
0
 
LarryDAHAuthor Commented:
Both servers are Dcs and both have AD installed. Below is the ipconfig for the old server:

Windows IP Configuration
   Host Name . . . . . . . . . . . . : dah01
   Primary Dns Suffix  . . . . . . . : ourdomain.org
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : ourdomain.org

Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP NC7760 Gigabit Server Adapter
   Physical Address. . . . . . . . . : 00-0F-20-12-23-56
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.0.10
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Default Gateway . . . . . . . . . : 192.168.0.3
   DNS Servers . . . . . . . . . . . : 192.168.0.10
                                                 192.168.1.10
-------------------------------------------------------------------

The new server is:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : do-dns01
   Primary Dns Suffix  . . . . . . . : ourdomain.org
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ourdomain.org

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : HP NC7761 Gigabit Server Adapter
   Physical Address. . . . . . . . . : 00-15-60-12-23-56
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.10
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Default Gateway . . . . . . . . . : 192.168.0.3
   DNS Servers . . . . . . . . . . . : 192.168.1.10
                                                 192.168.0.10
0
 
martin_babarikCommented:
Thanks a lot. Are the zones AD integrated? If they are they will contain identical information.
Ipconfig output seems to be very correct, if I didn't overlooked something.
I recommend to try using "ipconfig /flushdns" on the computer from which you are trying to ping. Also check manually if there was created the PTR record in reverse lookup zone for both servers.
0
 
LarryDAHAuthor Commented:
How do I check if the AD zones are integrated? I used the wizard on the new server when I set up AD and DNS and I do not remember that it asked about intetration, I assume they would be.

Flushdns did not change the ping -a from just the server name on the new server. It still does not bring back the FQDN and it is using the new server as the logon server.

The servers are in different subnets. Both DNS servers are listed as Name Servers in the DNS for all subnets in the Reverse Lookup zones (and also as name servers under the domain name in the forward look up zones on both servers). Each DNS server is also listed in its own reverse lookup zone in its own subnet with a PTR and as a Name server, however in all the other subnets both DNS servers only have Name Servers and no PTR records.
0
 
LarryDAHAuthor Commented:
I found the problem, but first to answer your questions. I looked and both DNS servers are marked as AD integrated. While under properties I looked under Zone Transfers and on the old server transfers are allowed to other servers listed on the Names servers tab (which does show the new DNS server) but on the new server that is not checked. Should I allow zone transfers from the new server to the old also?

Doing some research on FQDN I remembered that I can do nslookup to see my named servers and when I did that on the Blackberry server (where my original problem started)  that has used the new DNS server as the logon server it showed my a named server that was on the public side. I found that I had ATT (4.2.2.1) as my 3rd choice for a forwarder on the new server. Somehow the Blackberry server picked 4.2.2.1 and that is why my FQDN was not working. I had to change it in the registry to get it to go away but after I did that my Blackberry server could ping the new DNS server and get a FQDN
0
 
martin_babarikCommented:
Good to hear you found a solution.
Regarding your question - to be honest I'm not sure, but as both zones are AD integrated, as far as I know there will be no more standard transfers and everything will be replicated through AD, so I guess you don't need to allow zone transfers at all.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.