Skip to main content

DNS resolver failure

Comments

8 comments

  • cPRex Jurassic Moderator
    Hey there! Can you ensure that port 53 is open for traffic on your machine with that new IP address? Without that port opened for traffic there will be odd behavior with the DNS system.
    0
  • Mactabby
    I believe it is - output from netstat: tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 866/pdns_server
    0
  • cPRex Jurassic Moderator
    netstat would only tell us what is happening locally. I like to use nmap to test specific ports from an external machine, with this command: nmap -sU x.x.x.x -p 53
    where "x.x.x.x" is the IP address of the server.
    0
  • Mactabby
    Hi - output from nmap as requested: Host is up. PORT STATE SERVICE 53/udp open|filtered domain
    0
  • cPRex Jurassic Moderator
    That certainly looks normal to me. It might be time to reach out to your host to see if they have experienced any resolver issues if you are continuing to get that message nightly.
    0
  • Mactabby
    Just to close this, the problem was indeed with the hosts and they needed to tweak the routing and rebuild the network for me. All sorted now.
    0
  • cPRex Jurassic Moderator
    Thanks for the follow up!
    0
  • hmaddy
    How to do this.??? can you please share its steps
    0

Please sign in to leave a comment.