• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2409
  • Last Modified:

DNS error "bad referral"

Can anyone tell me what the named error:
Jul 30 09:37:27 xxxxx named[6192]: bad referral (com !< aol.com)

Thanks
0
PAdajar2
Asked:
PAdajar2
1 Solution
 
ahoffmannCommented:
http://www.acmebw.com/askmrdns/bind-messages.htm

bad referral (state.il.us !<  SOS.STATE.IL.US)
CATEGORY: response-checks
SEVERITY: info
PAGE:
FURTHER INFO:

Indicates that while querying the SOS.STATE.IL.US name servers, your name server was referred to the state.il.us name
servers.  Since a referral should always point to name servers authoritative for descendant zones, this is an error.  The name
server that sent the referral is probably misconfigured, and not authoritative for the zone delegated to it.
0
 
PAdajar2Author Commented:
my understanding of this is that it is not a configuration error on my part. is this accurate?
0
 
ahoffmannCommented:
Just read the text ...

>  The name server that sent the referral is probably misconfigured,

If your name server produced this message, then it's yours.
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
PAdajar2Author Commented:
the message was contained in the log of my name server. if this is a configuration error on my part then what exactly is misconfigured? my zone files or my named.conf??

thanks
0
 
ahoffmannCommented:
usually your named.conf
0
 
PAdajar2Author Commented:
Here is my named.conf its pretty simple and was using the same conf file ever prior to the messages showing up in the log.

Any idea where the error is?


// BIND Config File

options {
        directory "/var/named";
        forwarders {198.6.1.195; 198.6.100.25; };
};

zone "xxxxx.com" in {
        type master;
        file "masters/db.xxxxx.com";
        allow-transfer {198.6.1.18; 198.6.1.19;
        137.39.110.20; 137.39.110.134; };
};

zone "yyyyy.xxxxx.com" in {
        type master;
        file "masters/db.yyyyy.xxxxx.com";
};

// Secondary server zone data(client zone info)


// Cache and inverse lookup zone data

zone "." in {
        type hint;
        file "db.named.cache";
};

zone "0.0.127.in-addr.arpa" in {
        type master;
        file "masters/db.127.0.0";
};

Thanks
0
 
lrmooreCommented:
PAdajar2,
No comment has been added lately (725 days), so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area for this question:

RECOMMENDATION: Accept PAdajar2's answer http:#6341731 and Refund

Please leave any comments here within 7 days.

-- Please DO NOT accept this comment as an answer ! --

Thanks,

lrmoore
EE Cleanup Volunteer
0
 
YensidModCommented:
Question is PAQ'd and points refunded.

YensidMod
Community Support Moderator @Experts Exchange
0
 
Handy HolderSaggar maker's bottom knockerCommented:
zone "." in {
       type hint;
       file "db.named.cache";

Explains the bad referral - they have set it up as if it is the root of the DNS namespace when clearly it isn't.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now