BIND DNS not returning records.

Gertjan

….
Jan 2 12:01:59 named 48149 setsockopt(28, TCP_FASTOPEN) failed with Protocol not available
......

You saw the "failed" ?
So copy "setsockopt(28, TCP_FASTOPEN) failed with Protocol not available" into Google and you will know more.

curtisgrice

Ok so how do I downgrade to 9.10.4P2? I don't see any documentation on downgrading packages.

Gertjan

Can't tell.
Packages related to OS (FreeBSD) and pfSense use very strict rules.
All depends what you have right now, etc.

kpa

I doubt downgrading the BIND package would do any good, cure the problem, not the symptoms.

curtisgrice

Ok but more to the issue, BIND IS working (just not the way I need). I can see it accepts the quere and sends a response, just not the correct one. I feel like this is one of those missing ; kind of issues.

johnpoz

Don't cross post, and dig up threads from year ago..

What part in your zone file do you think is correct about this?

@ IN NS 192.168.1.1.

So you think its ok to put in an IP for your NS record?

curtisgrice

@johnpoz:

Don't cross post, and dig up threads from year ago..

Sorry about that It seemed related.

@johnpoz:

What part in your zone file do you think is correct about this?

@ IN NS 192.168.1.1.

So you think its ok to put in an IP for your NS record?

What makes you think I know so much about DNS? ;)

johnpoz

Nothing from that zone file - but that you would be running bind vs just unbound or or the dnsmasq forwarder seems to point to you know something about dns and need the functionality of bind ;)

Fix your zone up and it will work just fine..

curtisgrice

This may be against best practice but doesn't this just cause a recursive lookup? Why not just drop the name server IP into

@ 	 IN NS 	ns1.rack.center.
...
ns1 	 IN A  	192.168.1.1

vs

@ 	 IN NS 	192.168.1.1

I feel like i'm still missing something.

johnpoz

https://www.ietf.org/rfc/rfc1035.txt

NSDNAME A <domain-name>which specifies a host which should be authoritative for the specified class and domain.

How is 192.168.1.1 a domain-name? I suggest you read the rfc ;)

Run your zone file through checkconf..

Yes your NS record will need a A record for its name pointing to the IP, etc. .. But an IP is not a valid NS record..</domain-name>