The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

bind problems $ORIGIN?

Discussion in 'Bind / DNS / Nameserver Issues' started by phantom2, Apr 22, 2004.

  1. phantom2

    phantom2 Well-Known Member

    Joined:
    Jan 3, 2004
    Messages:
    59
    Likes Received:
    0
    Trophy Points:
    6
    Hi,
    We just set up our cluster with 2 new dedicated name servers.

    We moved a bunch of accounts over to another server in the cluster and none of the domains will come up. Plus Bind is failing with the rndc error. We've tried /scripts/fixnamed
    and /scripts/fixndc and there is no dash in between rndckey in named.conf

    What's strange is the zone files for the domain we moved over have an entry I've not see in other zone files. Here's an example.

    $ORIGIN .
    $TTL 14400 ; 4 hours
    zoneclicks.com IN SOA ns1.phantomhosting.com. webmaster.phantomhosting.com. (
    1019416301 ; serial
    28800 ; refresh (8 hours)
    7200 ; retry (2 hours)
    3600000 ; expire (5 weeks 6 days 16 hours)
    86400 ; minimum (1 day)
    )
    NS ns1.phantomhosting.com.
    NS ns2.phantomhosting.com.
    A 209.51.131.178
    MX 0 zoneclicks.com.
    $ORIGIN zoneclicks.com.
    ftp CNAME zoneclicks.com.
    localhost A 127.0.0.1
    mail CNAME zoneclicks.com.
    www CNAME zoneclicks.com.

    Does anyone know what the $ORIGIN thing is? The above is an example of a zone of a domain that was moved to another server in the cluster.
     
  2. Myacen

    Myacen Well-Known Member

    Joined:
    Apr 6, 2002
    Messages:
    222
    Likes Received:
    0
    Trophy Points:
    16
    The zone is corrupted
     
  3. TySoft

    TySoft Member

    Joined:
    Aug 21, 2003
    Messages:
    23
    Likes Received:
    0
    Trophy Points:
    1
    I had this problem. I deleted all the zone files from the affected server (in this case the old slave, only started with clustering... worked fine with the old master/slave system).

    Then I used the Synchronize DNS Records with Primary Nameserver and it redownloaded from the other cluster server properly.
     
Loading...

Share This Page