Unable to ping FQDN

Hi,

Building a lab again, and having trouble joining a server into a domain.

Maybe im missing something here. Here's the problem.

When I do a NSLOOKUP, from a server that is about to be joined to REALESTATE.COM, the FQDN of the DC gets returned with its IP address as seen from the enclosed file.

But, when I try to ping the DC FQDN, it unables to find the host name SRV-DC. That's not correct, because in my FORWARDLOOKUP zone, I have a host record of SRV-DC with an IP address of 169.254.0.120. I have a record also in REVERSELOOKUP zone - IP to FQDN.

Not sure at this stage where to look for this issue.


error.bmp
LVL 7
mcse2007Asked:
Who is Participating?
 
ActiveDirectorymanConnect With a Mentor Commented:

first, I would clear your dns cache since you just made a negative query.

ipconfig /flushdns  /registerdns

second,  that message means that you have a name resolution problem.

The problem is that you are using an invalid address range for dns resolution. You cannot use the 169.254.x.x range. Your network interfaces must be configured with a valid range such as 192.168.x.x or 10.0.x.x.

Check out this article

http://technet.microsoft.com/fr-fr/library/dd378975(WS.10).aspx
0
 
TheTullCommented:
Can you do an ipconfig /all please and copy the output here.  Also, why are you using the 169.254 IP range?  That is reserved for situations where you don't have a normal IP to use either statically or through DHCP.
0
 
mcse2007Author Commented:
I figured that out too.....ActiveDirectoryman...as soon as I've changed my ip address to class A, it automatically fixed the issue, right after I' posted this issue here.

But, you were on the money.
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.