Link to home
Start Free TrialLog in
Avatar of Mohammed Azhar
Mohammed Azhar

asked on

Dns Servers Not Resolving Certain Addresses

I had this question after viewing DNS not resolving for specific website.

I have a same Issue like. Our DNS server not responding to the certain address
Avatar of Mahesh
Mahesh
Flag of India image

what dns you are using?

have you tried Google DNS?

8.8.4.4
8.8.8.8

ensure that from your server you are able to reach / telnet above IPs on 53 port
Avatar of Mohammed Azhar
Mohammed Azhar

ASKER

I've used 8.8.8.8 and it solves an ip
but  when i use the resolver x.x.x.x it says server fail.
In total
I’ve did nslookup and it is simply returning an error.
I’ve tried to use dig and I’ve found www.samsungcentral.com is resolving to c-name record to samsungcentral.com but here samsungcentral.com is not resloving the ip.
Looks correct... shows 198.46.84.37 for your domain + CNAME from www to domain...

Maybe you're using some sort of internal DNS caching server which is broken.

imac> dig samsungcentral.com any

;; <<>> DiG 9.8.3-P1 <<>> samsungcentral.com any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31626
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;samsungcentral.com.		IN	ANY

;; ANSWER SECTION:
samsungcentral.com.	599	IN	A	198.46.84.37
samsungcentral.com.	3599	IN	NS	ns11.domaincontrol.com.
samsungcentral.com.	3599	IN	NS	ns12.domaincontrol.com.
samsungcentral.com.	3599	IN	SOA	ns43.domaincontrol.com. dns.jomax.net. 2018041002 28800 7200 604800 600
samsungcentral.com.	3599	IN	TXT	"google-site-verification=oEq8TRhozoXo6qcLE8eysQjmAwQ47dBzs7cLh9MC4CE"

;; Query time: 149 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Sep 21 16:34:59 2018
;; MSG SIZE  rcvd: 239

Open in new window

WHat is the fix or how can i make sure that internal DNS caching server is broken.
Fix for broken internal server is to either...

1) Have the person who setup this facility debug + fix problem.

2) Circumvent using internal caching server by setting your DNS lookups to use a set of public servers... like...

1.1.1.1 - CloudFlare (very fast)
8.8.8.8 - Google
8.8.4.4 - Google
huh?? if we are using Windows and ad dns use s conbo of forward lookup zones to manipulate external dns requests internally before they become external dns requests

also ad dns should be using root hints ms rec official or a forwarder to your isp dns and client and server computers use only dc for dns which use only root hints or isp dns

#1 in Ireland
Verify that all your AD DNS server have the same forwarding and that they can all ask questions for unknown domains to that forwardinf server.
if DNS1 can query 1.1.1.1 or 8.8.8.8 and DNS2 cannot get a valid answer from DNS2.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members 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.