Skip to main content

Nameserver not working

retechpro
I"ve setup a new server on ovh and facing strange issues. I didn"t Faced these type of issues in past. I"ve setup a server completely and create a nameserver dns1.domain.com dns2.domain.com. I"ve added this nameserver in domain but the domain still not showing ip. Dns not propagated from last 36 hours. I"ve already created the Records and A entries in domain. And created private nameserver in domain too. still ns is not propagating. My old servers nameserver are working fine. It propagate within 15 mints. should anyone know how to fix it

Comments

20 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! Have you created the namservers at the registrar level as well?
    0
  • cPRex Jurassic Moderator
    In general, you'd want to do the following: -create the nameservers at the registrar -add A records for the nameservers inside the DNS zone for domain.com (just like creating A records for any other subdomain) -add NS records for the nameservers Once that is done, and the DNS has a chance to propagate, I would expect them to start working. If that isn't working, your machine may not have the proper networking connections. You can run this command *from an external server or your local workstation* to check the inbound connections that the nameserver will use: nmap -sU x.x.x.x -p 53
    where "x.x.x.x" is your server's IP address. If that shows as being filtered or doesn't work at all, you'll need to speak with your host about how to resolve that.
    0
  • quietFinn
    -create the nameservers at the registrar

    and remember to set the nameserver IPs to the nameservers at the registrar.
    0
  • retechpro
    I"ve created private NS/Glue records in domain. Add A record in Domain Created NS in Whm in basic webhostmanager at then end. When in Check dns of dns1.domain.com it show correct ip. But when i add these nameserver for domain it did not work. What could be the reason behind it
    0
  • cPRex Jurassic Moderator
    It sounds like you didn't do anything at the registrar level.
    0
  • retechpro
    I"ve setup lot of servers but this server is creating issue. I"ve done registrar level. created Private Nameserver dns1.domain.com point to ip Dns2.domain.com point to ip add A record for dns1 and dns2 Still face same issue
    0
  • cPRex Jurassic Moderator
    It might be best to create a ticket so we can check this directly.
    0
  • retechpro
    It might be best to create a ticket so we can check this directly.

    Ticket id = #95074287 Now waiting what the issue inside it
    0
  • vanessa
    Does querying your DNS server directly return any results? This should narrow whether its an issue with the glue records or the nameserver itself. dig @yournameserverip dns1.yourdomain.com How did you create the records? Zone editor? Check /var/log/messages for bind errors.
    0
  • retechpro
    I"ve already added glue records. Add A record in Cloudflare as i am using cloudflare. dig @ip domainame.com Show ns dig @ip dns1.yourdomain.com Show server ip it work fine within the network only. Ns is not working outside the network. I"ve contacted the server Support but they are unable to do any help regarding this.
    0
  • vanessa
    so you've confirmed that your DNS servers are working internally - is this bind or pdns? Do you mind DM'ing me your domain?
    0
  • retechpro
    Using pdns. I"ve reinstalled servers 8 times to check the issue. Currently domain hosted on this server is : kickflickenterprises.com
    0
  • vanessa
    So we get to right around here: ;; Received 1212 bytes from 2001:500:2::c#53(c.root-servers.net) in 20 ms kickflickenterprises.com. 172800 IN NS dns1.dnscloudserver.com. kickflickenterprises.com. 172800 IN NS dns2.dnscloudserver.com. CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q2D6NI4I7EQH8NA30NS61O48UL8G5 NS SOA RRSIG DNSKEY NSEC3PARAM CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20230615042524 20230608031524 46551 com. opW1EZF0WaMz+df3vPSEQppiJ1Lj//YDFV/jDliPAJW+mSiYmFbJVQrq aNXtOgLzSD9VGKZ1ct/giCaP4pMt6RCCFaIKgpf7VwTCKtvOfV2IImZ5 y9iV8EQqx3oSFAD4BrchjjgsVzo+6k9pp1tyLdlbfO83DUibCyFuRNAc Tnsahwk274qiOF40DtdAXdxT1AMGusu4KTOOKoaW/hicxw== IAUCQCIB7G0M5QUM8QGARQ3UVA60KD65.com. 86400 IN NSEC3 1 1 0 - IAUD5NEJN17KRLF85U6TONS8HCPUHHFA NS DS RRSIG IAUCQCIB7G0M5QUM8QGARQ3UVA60KD65.com. 86400 IN RRSIG NSEC3 8 2 86400 20230614042143 20230607031143 46551 com. losKXH8gWlJxbiFkvIbTtSfmnGUKmlaPilFTMm3sOSmNjZMK/2ugzGlK Lf9IK6v74aRB3G6+/7c3OkN7zyA/rZd53eR++hv8bMsYBhgm2LcrChDh 6mPfHqvFCf1kR5/H5Y/1Ld3+Tj6isq9Vik1V0d+ksygyy6U6Bl80VL0L ktjwtAN574VDEvvyQ8pHLbUdv12h8Lq4b8vfE3cSCzl33g== ;; Received 687 bytes from 192.12.94.30#53(e.gtld-servers.net) in 184 ms ;; connection timed out; no servers could be reached
    Then it times out. I cannot make any queries to dns1.dnscloudserver.com, etc - if these are the correct nameservers, it looks like port 53 is blocked. Please check your firewall and make sure UDP and TCP port 53 are open. ; <<>> DiG 9.16.1-Ubuntu <<>> @dns1.dnscloudserver.com 8.8.8.8 ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
    0
  • retechpro
    There is no firewall on server. I"ve contacted the datacenter they said we do not block any port. 53 port are open on server. Checked everything on our end. they also said everything is working fine within the Network. I"ve told them it is not working outside the network. I"ve opened a ticket. Let"s see where is issue. As pdns is working fine. We have also check bind.But same response. .
    0
  • vanessa
    It really looks like a firewall issue to me - I can't get a connection on port 53 at all, that's why the nameserver is not resolving externally. Maybe just check: systemctl stop firewalld
    0
  • retechpro
    It really looks like a firewall issue to me - I can't get a connection on port 53 at all, that's why the nameserver is not resolving externally. Maybe just check: systemctl stop firewalld

    already told there is no firewall. Systemctl status firewalld Did not found systemctl stop firewalld did not work happen because there is no firewall on server.
    0
  • vanessa
    already told there is no firewall. Systemctl status firewalld Did not found systemctl stop firewalld did not work happen because there is no firewall on server.

    Well, something is blocking port 53. You're already talking to OVH so hopefully they can resolve for you. No need to get testy :)
    0
  • retechpro
    Well, something is blocking port 53. You're already talking to OVH so hopefully they can resolve for you. No need to get testy :)

    You was right. There was gaming firewall that block all udp port. I"ve disable firewall now ns is working fine. Thank you for you help
    0
  • retechpro
    hi vanessa, yesterday suddenly my all sites goes down without any issue. WHM/Cpanel is working. Site working with cloudflare ns. Server dns is not working. datacenter said UPD/TCP port 53 is open. I have checked pdns. it is working also move on bind to check. it also working but dns is not working on both. I have update cpanel etc. but still did not find the solution.
    0
  • cPRex Jurassic Moderator
    @retechpro - can you be more specific when you say DNS isn't working? Are you not able to look up any DNS records for any domains on the system?
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post