Author Topic: BIND DNS Server Fail when Adding google._domainkey  (Read 1219 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
BIND DNS Server Fail when Adding google._domainkey
« on: January 18, 2021, 07:16:35 AM »
Could somebody advise?

We're trying to add google._domainkey TXT record, as instructed by Google where we have our Mail server, and the record is added fine through the DNS file editor, but when restarting BIND DNS, we receive this warning: https://prnt.sc/x3t9cx

The only domain key allowed is the default._domainkey; removing the default._domainkey and just leaving google._domainkey, leaving both don't work either.

This is what the journalctl -xe shows:

Jan 17 23:01:22 host.domain.tld systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
-- Subject: Unit named.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has begun starting up.
Jan 17 23:01:22 host.domain.tld bash[22531]: zone localhost.localdomain/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone localhost/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 0.in-addr.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone domain.tld/IN: loaded serial 2021010424
Jan 17 23:01:22 host.domain.tld bash[22531]: zone ns1.domain.tld/IN: loaded serial 2020122901
Jan 17 23:01:22 host.domain.tld bash[22531]: zone ns2.domain.tld/IN: loaded serial 2020122900
Jan 17 23:01:22 host.domain.tld bash[22531]: zone host.domain.tld/IN: loaded serial 2020122996
Jan 17 23:01:22 host.domain.tld bash[22531]: dns_rdata_fromtext: /var/named/DOMAIN.WITH.ISSUE.db:23: syntax error
Jan 17 23:01:22 host.domain.tld bash[22531]: zone DOMAIN.WITH.ISSUE/IN: loading from master file /var/named/DOMAIN.WITH.ISSUE.db failed: syntax error
Jan 17 23:01:22 host.domain.tld bash[22531]: zone DOMAIN.WITH.ISSUE/IN: not loaded due to errors.
Jan 17 23:01:22 host.domain.tld bash[22531]: _default/DOMAIN.WITH.ISSUE/IN: syntax error
Jan 17 23:01:22 host.domain.tld systemd[1]: named.service: control process exited, code=exited status=1
Jan 17 23:01:22 host.domain.tld systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
-- Subject: Unit named.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has failed.
--
-- The result is failed.
Jan 17 23:01:22 host.domain.tld systemd[1]: Unit named.service entered failed state.
Jan 17 23:01:22 host.domain.tld systemd[1]: named.service failed.
Jan 17 23:01:25 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:01:25 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=39110 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:01:25 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:01:25 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:01:41 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:01:41 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:01:41 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:01:41 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=49734 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:02:00 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:02:00 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:02:00 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:02:00 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=59062 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:02:01 host.domain.tld systemd[1]: Created slice User Slice of securev.
-- Subject: Unit user-1001.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-1001.slice has finished starting up.
--
-- The start-up result is done.

Appreciate your prompt response.

Offline
*
Re: BIND DNS Server Fail when Adding google._domainkey
« Reply #1 on: January 18, 2021, 09:30:03 AM »
as visible in the error message you have an error at line 23

dns_rdata_fromtext: /var/named/DOMAIN.WITH.ISSUE.db:23: syntax error
VPS & Dedicated server provider with included FREE Managed support for CWP.
http://www.studio4host.com/

*** Don't allow that your server or website is down, choose hosting provider with included expert managed support for your CWP.

Offline
*
Re: BIND DNS Server Fail when Adding google._domainkey
« Reply #2 on: January 18, 2021, 04:28:59 PM »
Thanks and that's the problem, I don't see the error in what Google sent me to enter:

google._domainkey 14400 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgid3fOVOc2s3fxaASywa9VK3Z49CElqqEYiJx4kAkGD6qpUKTY487OBR3L1L1wFLk2NWWJpn+xpFj5P/070TJfWv3mAKt2YZr/woHgxV+HWNixB46TDBOcNmcY5hZJsrAO7CXMgAppzVgmBgBC7K66U0CMqfpeQZQ5G198AY3cHhIduj/XksbD8EQXHxxe0mUiiCpQSiB54H0JddnFT80z03WYP59xKCwVFNh3h5Aq/Ai64nT9crjGh7uQNJQqI+gqFDgUMgMKdE8VhjlLe526lM2akA1N79TuM2UA6Rq0nAWLpq2xPCsTqN6gVzBlMCId7wo1rUpmvh6e+nAMMRXwIDAQAB"

Can you spot it?

Re: BIND DNS Server Fail when Adding google._domainkey
« Reply #3 on: January 18, 2021, 05:54:51 PM »
@ProComm?  ::)
Record is too long: split it.

Offline
*
Re: BIND DNS Server Fail when Adding google._domainkey
« Reply #4 on: January 18, 2021, 06:00:04 PM »
@cynique sorry for the "silly" question, but how can a DNS record be split it without breaking it?

Re: BIND DNS Server Fail when Adding google._domainkey
« Reply #5 on: January 18, 2021, 06:07:13 PM »
@cynique sorry for the "silly" question, but how can a DNS record be split it without breaking it?
Yahoo! search works really well..
https://www.mailhardener.com/tools/dns-record-splitter

Offline
*
Re: BIND DNS Server Fail when Adding google._domainkey
« Reply #6 on: January 18, 2021, 06:16:30 PM »
@cynique you are a GENIOUS.

It did work; thank you!

Re: BIND DNS Server Fail when Adding google._domainkey
« Reply #7 on: January 18, 2021, 07:30:55 PM »
@cynique you are a GENIOUS.

It did work; thank you!
Nah, just had come across the issue, some weeks/months ago. ;)

You're welcome.