DNS configuration (BIND), site not accessible to everyone

Discussion in 'Site & Server Administration' started by Gray Fox, Sep 18, 2009.

  1. #1
    Since I'm pretty much new to Linux, I followed some tutorial on setting up BIND. Everything seemed to be working perfectly, until I found out that my domain is not accessible for everyone, it seems to redirect to godaddy nameservers, even tho I set them up with godaddy (NS1.MYSITE.COM and NS2.MYSITE.COM) which are both on the same IP as my server (208.53.131.132).

    I could REALLY use some help here, since it's bugging me for days now.
    One example of wrong nameservers being used is this browser proxy http://foxcat.net.ru/index.php?so=http://anisoc.com&hl=3e5 (but it seems like it's banned from godaddy so it wont show up anything).
     
    Last edited: Sep 18, 2009
    Gray Fox, Sep 18, 2009 IP
  2. ohteddy

    ohteddy Member

    Messages:
    128
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    28
    #2
    The good news is that you're configured and working from my end,
    the GTLD-SERVERS have the correct information.

    So the question is really what are the users problems here. Sometimes
    you need to run 'ipconfig/flush' from a windows machine to clear out any
    old cached data. Other than that you'll just have to wait until ISP's update
    their cached records with your new info. I've seen this take up to 72 hours.
     
    ohteddy, Sep 18, 2009 IP
  3. Gray Fox

    Gray Fox Well-Known Member

    Messages:
    196
    Likes Received:
    8
    Best Answers:
    0
    Trophy Points:
    130
    #3
    Thank you for your response, ohteddy, seems like it was my ISP acting strange and looks like they finally refreshed their DNS.
    At first when I did "nslookup mysite.com" they provided me with its old IP (godaddy nameservers), but now the site works for me without having to edit Windows' hosts file.

    But something's still bugging me, I'm not sure if I configured it right for the apache. When i add
    
    <VirtualHost *:80>
        DocumentRoot /var/www/phpmyadmin
        ServerName pma.mysite.com
    </VirtualHost>
    
    Code (markup):
    in httpd.conf, every request (mysite.com; www.mysite.com; pma.mysite.com) gets redirected to that directory. I know it is an apache issue and I may repost this in its subforum, but I'm still not sure if mysite.com.zone is configured properly for that subdomain.
     
    Last edited: Sep 18, 2009
    Gray Fox, Sep 18, 2009 IP
  4. ohteddy

    ohteddy Member

    Messages:
    128
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    28
    #4
    I'm not much of an apache guy myself, but you may want to try 'ip.add.re.ss:80' instead of *:80.
     
    ohteddy, Sep 18, 2009 IP
  5. GNetCoder

    GNetCoder Peon

    Messages:
    68
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    0
    #5
    Are there any virtualhost entries above pma.mysite.com? if you have directives like:

    ServerName mysite.com
    ServerName *.mysite.com
    ServerAlias *.mysite.com

    etc, they will take precedence.
     
    GNetCoder, Sep 18, 2009 IP