Solved

DNS Issue

Posted on 2014-02-10
11
302 Views
Last Modified: 2014-02-17
How should i resolve this issues :

http://www.intodns.com/geforce.com.au

WARNING: Looks like the parent servers do not have information for your TLD when asked. This is ok but can be confusing.

ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
203.30.165.148

Detail:
We have 3 Windows DNS server 2 (.50 (Primary) &.51 (secondary)) are on same subnet and .148(secondary) are different.
Windows firewall is already off and port 53 allow on firewall. if i am going to resolve primary DNS IP on .148 server i receive the error "Unable to Resolve FQDN" kindly review attach image.
.51 FQDN is resolve without any issue.

Any Suggestion?
unable-to-resolve.jpg
0
Comment
Question by:Geforce
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3
  • 2
11 Comments
 
LVL 21

Expert Comment

by:Radhakrishnan R
ID: 39849274
Hi,

Are you able to ping .50 from other server? Is the .50 server's DNS AD integrated? have you tried to remove and re-add?
Is the forwarders resolving fine?

Perform a nslookup against .50 address and host name and see it resolves? if not, it's missing some DNS entries somewhere in the zone.
0
 

Author Comment

by:Geforce
ID: 39849288
Hi,

Thanks for the reply,
Yes i am able to ping .50 from .148 server.
No AD, Its a Windows web server 2008R2 .
No i didn't try to remove DNS server from .148 because it was working fine before and we just start to receive above errors.
No DNS Forwarder set.

I perform a nslookup against .50 from .148 server and error receive "Unknown can't fine .50: non-existent domain." nslookup against .51 is from .148 is working fine.

So what actually i am missing because i check the all the DNS entries and all three server entries are identical.
0
 
LVL 21

Expert Comment

by:Radhakrishnan R
ID: 39849302
Hi,

Probably you are missing a host A record for that server. Create an A record for the hostname which pointing to the .50 address and see it's resolving fine?
0
Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

 

Author Comment

by:Geforce
ID: 39849339
Hi,

Host A record is already exist. i am using Google DNS (8.8.8.8/8.8.4.4) in my TCP/IP setting on .50 server and i am not able to resolve host name on .50 server. I think if i used my ISP DNS than problem will resolve. What you think??
0
 
LVL 21

Expert Comment

by:Radhakrishnan R
ID: 39849419
Hi,

Yes, that's the issue lying here. I hope the .50 server is located in your internal domain? if so, you need to put the first DC's IP address as a primary DNS and additional DC as a alternate DNS addresses.

Always, put your ISP's DNS in forwarders list. So, remove the Google DNS from the network card adapter and put internal DNS servers's IP instead. Add the ISP's DNS, Google DNS in forwarders list.
0
 

Author Comment

by:Geforce
ID: 39849570
Hi,

we don't have DC's. we are hosting company. .50 is our primary DNS server and .51/.148 is secondary DNS. I will try to put ISP DNS, if you have any other thought. kindly share with me, thanks for your support.
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 39849577
Does all 3 DNS servers are published on internet ?
0
 

Author Comment

by:Geforce
ID: 39849625
Yes all three DNS servers are published on internet.
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 39849722
If you did nslookup from 50 server for itself, does it resolves, or here it gives you error ?

Since your 50 server points to Google DNS, where those another servers (148 and 51) points for DNS ?

Does 50 server resolves from 51 server ?

I think you can try by pointing both servers to Google DNS and then check, Then it should go in perfect order such as Root\TLD

Mahesh
0
 

Accepted Solution

by:
Geforce earned 0 total points
ID: 39855466
Thanks Mahesh and Radhakrishnan for your support and valuable suggestion.
My issue has been resolved basically port 53 blocked on .148 server. now port is open and everything back to normal.
0
 

Author Closing Comment

by:Geforce
ID: 39864349
DNS port is block on my another server so i checked it and resolve the issue
0

Featured Post

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question