dns hosting doesn't seem to be working

Discussion in 'General' started by andyreynolds, Feb 19, 2007.

  1. andyreynolds

    andyreynolds New Member

    I have followed the instructions for creating your own name servers so I have got ns1 and ns2 .srhosting.net. which look up to their respective IP addresses. I have created a master zone for the domain name mysrhosting.com but it doesn't seem to transfer to my servers. When I look up the domain with dnstuff.com it returns my name servers as being the right ones but that is about it. I have also noticed that both of my servers are outputing the welcome to fedora apache test page. I have seen that on other fuctioning servers that the first IP address if you go to it comes with shared IP?? and the second server has this test page. Both of my servers have their test pages and I have followed the instructions whereby creating a DNS master and slave zone on the respective servers. I have given it 3 days since I transfered the domain to my name servers, but it still doesn't work. All the services on both servers are working ok and the DNS is set to ns1 and ns2 srhosting.net and their is no firewall on the router as I can access them from outside. What do I need to do???
    Cheers
    Andy
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Please check your DNS servers with the following command executed on the shell of each server:

    dig @localhost yourdomain.com
     
  3. andyreynolds

    andyreynolds New Member

    dig command

    Hi
    I have done that and each server returns their respective IP address. If i look up ns1 or ns2.srhosting.net at dnsstuff.com it returns the correct IP addresss of the server.
     
  4. andyreynolds

    andyreynolds New Member

    name server error

    when i look up the domain mysrhosting.com it returns the following error
    NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).

    Does this mean BIND on my servers isn't working correctly even though they are configured right and the service is working?
     
  5. andyreynolds

    andyreynolds New Member

    mysrhosting.com error message from dns

    Searching for mysrhosting.com ALL record at l.root-servers.net [198.32.64.12]: Got referral to b.gtld-servers.net. (zone: com.) [took 85 ms]
    Searching for mysrhosting.com ALL record at b.gtld-servers.net. [192.33.14.30]: Got referral to ns2.srhosting.net. (zone: mysrhosting.com.) [took 264 ms]
    Searching for mysrhosting.com ALL record at ns2.srhosting.net. [91.84.34.130]: Timed out. Trying again.
    Searching for mysrhosting.com ALL record at ns2.srhosting.net. [91.84.34.130]: Timed out. Trying again.
    Searching for mysrhosting.com ALL record at ns1.srhosting.net. [91.84.34.131]: Timed out. Trying again.
    Searching for mysrhosting.com ALL record at ns1.srhosting.net. [91.84.34.131]: Timed out. Trying again.
    Searching for mysrhosting.com ALL record at ns1.srhosting.net. [91.84.34.131]: Timed out. Trying again.
    Searching for mysrhosting.com ALL record at ns1.srhosting.net. [91.84.34.131]: Timed out. Trying again.

    even though I have got dns entries in both servers it comes up with these errors
     
  6. falko

    falko Super Moderator ISPConfig Developer

    Did you open port 53 (TCP and UDP!) on ns1 and ns2?
     
  7. andyreynolds

    andyreynolds New Member

    dns

    I ran the port scanner and it said they are all open. I have changed my name servers to ns3 and ns4 .teignmouthhosting.com and transfered the domain vsk-gbr.com to those name servers. The name servers point towards the 2 servers 91.84.34.133/134 from here you can access the ispconfig control panel on each server. The name server fields in both servers have been changed to accommodate ns3 and ns4 .teignmouthhosting.com, but I am still getting this error message '
    'NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).
    '
    I have checked with my isp and no ports are blocked and the router is set up correctly so I don't know what do you next??

    Searching for vsk-gbr.com ALL record at k.root-servers.net [193.0.14.129]: Timed out. Trying again.
    Searching for vsk-gbr.com ALL record at c.root-servers.net [192.33.4.12]: Got referral to C.GTLD-SERVERS.NET. (zone: com.) [took 7 ms]
    Searching for vsk-gbr.com ALL record at C.GTLD-SERVERS.NET. [192.26.92.30]: Got referral to ns4.teignmouthhosting.com. (zone: vsk-gbr.com.) [took 10 ms]
    Searching for vsk-gbr.com ALL record at ns4.teignmouthhosting.com. [91.84.34.134]: Timed out. Trying again.
    Searching for vsk-gbr.com ALL record at ns3.teignmouthhosting.com. [91.84.34.133]: Timed out. Trying again.
    Searching for vsk-gbr.com ALL record at ns3.teignmouthhosting.com. [91.84.34.133]: Timed out. Trying again.
    Searching for vsk-gbr.com ALL record at ns4.teignmouthhosting.com. [91.84.34.134]: Timed out. Trying again.
    Searching for vsk-gbr.com ALL record at ns4.teignmouthhosting.com. [91.84.34.134]: Timed out. Trying again.

    Is the root cause of this the fact that I don't see the shared ip at all on any of my servers, how would you get that?? do you need it to make my server to have the chance of hosting
     
    Last edited: Feb 20, 2007
  8. falko

    falko Super Moderator ISPConfig Developer

Share This Page