bind-users Digest, Vol 3004, Issue 2

Spears, Luke lspears at nrh-ok.com
Thu Sep 13 19:07:15 UTC 2018


Is there an upgrade guide for 9.11?

-----Original Message-----
From: bind-users [mailto:bind-users-bounces at lists.isc.org] On Behalf Of bind-users-request at lists.isc.org
Sent: Wednesday, September 12, 2018 1:26 PM
To: bind-users at lists.isc.org
Subject: [EXT] bind-users Digest, Vol 3004, Issue 2

[* EXTERNAL Email - please use caution when opening attachments or clicking links*]

Send bind-users mailing list submissions to
	bind-users at lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.isc.org/mailman/listinfo/bind-users
or, via email, send a message with subject or body 'help' to
	bind-users-request at lists.isc.org

You can reach the person managing the list at
	bind-users-owner at lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of bind-users digest..."


Today's Topics:

   1. Upgrade help with Bind 9.12 (Spears, Luke)
   2. Re: Issues configuring delegated subdomain zone (Bob Harold)
   3. Re: Upgrade help with Bind 9.12 (Matus UHLAR - fantomas)
   4. Error parsing file (BARAJAS BERMEJO, Sergio)


----------------------------------------------------------------------

Message: 1
Date: Wed, 12 Sep 2018 13:01:07 +0000
From: "Spears, Luke" <lspears at nrh-ok.com>
To: "'bind-users at lists.isc.org'" <bind-users at lists.isc.org>
Subject: Upgrade help with Bind 9.12
Message-ID: <caf2c5b058dd46e6808ca9f6c9eb767c at nrh-ok.com>
Content-Type: text/plain; charset="us-ascii"

I'm not sure how to go about requesting this but I am looking for information on upgrading from BIND 9.8 to 9.11 or 12 depending if it's ESV or not.  We are running Ubuntu 14.04

v\r
======================================
CONFIDENTIALITY NOTICE:

This e-mail communication and any attachments may 
contain confidential and privileged information for the use 
of the designated recipients named above. If you are not 
the intended recipient, you are hereby notified that you 
have received this communication in error and that any 
review, disclosure, dissemination, distribution, or copying 
of it or its contents is prohibited. If you have received 
this communication in error, please notify the sender 
immediately and destroy all copies of this communication 
and any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180912/ed7b791a/attachment-0001.html>

------------------------------

Message: 2
Date: Wed, 12 Sep 2018 10:47:30 -0400
From: Bob Harold <rharolde at umich.edu>
To: Sergio.BARAJAS at econocom.com
Cc: "bind-users at lists.isc.org" <bind-users at lists.isc.org>
Subject: Re: Issues configuring delegated subdomain zone
Message-ID:
	<CA+nkc8AatjsWsdVdChiOH7SwXnzzzJKpp-A0BY5mF2PGEMAXHQ at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Wed, Sep 12, 2018 at 5:49 AM BARAJAS BERMEJO, Sergio <
Sergio.BARAJAS at econocom.com> wrote:

> Hello,
> I have an issue configuring delegated subdomain zone from one NS to
> another one.
> For security reasons I will obviously not put real domain data (I imagine
> you will understand).
>
> Let's suppose that the delegated subdomain is:
> midominio.principal.hosting.com
> If we make a "dig" query, putting the hosting server's NS as the domain
> name server:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *dig @ns1.hosting.com <http://ns1.hosting.com>
> midominio.principal.hosting.com <http://midominio.principal.hosting.com> ;
> <<>> DiG 9.10.3-P4-Debian <<>> @ns1.hosting.com <http://ns1.hosting.com>
> midominio.principal.hosting.com <http://midominio.principal.hosting.com> ;
> (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<-
> opcode: QUERY, status: NOERROR, id: 40831 ;; flags: qr rd; QUERY: 1,
> ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3 ;; WARNING: recursion requested but
> not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096
> ;; QUESTION SECTION: ;midominio.principal.hosting.com
> <http://midominio.principal.hosting.com>. IN A ;; AUTHORITY SECTION:
> midominio.principal.hosting.com <http://midominio.principal.hosting.com>.
> 125 IN NS sb2.principal.hosting.com <http://sb2.principal.hosting.com>.
> midominio.principal.hosting.com <http://midominio.principal.hosting.com>.
> 125 IN NS sb1.principal.hosting.com <http://sb1.principal.hosting.com>. ;;
> ADDITIONAL SECTION: sb1.principal.hosting.com
> <http://sb1.principal.hosting.com>. 125 IN A xxx.xxx.xxx.52
> sb2.principal.hosting.com <http://sb2.principal.hosting.com>. 125 IN A
> xxx.xxx.xxx.53 ;; Query time: 12 msec ;; SERVER:
> 31.193.224.20#53(31.193.224.20) ;; WHEN: Wed Sep 12 08:09:36 CEST 2018 ;;
> MSG SIZE rcvd: 133*
>
> From which we deduce several things:
>
>
>    1. That in the zone principal.hosting.com of the main server of the
>    hosting there are created two registers of type A:
>    1.
> *sb1.principal.hosting.com <http://sb1.principal.hosting.com>. 125 IN A
>       xxx.xxx.xxx.52 sb2.principal.hosting.com
>       <http://sb2.principal.hosting.com>. 125 IN A xxx.xxx.xxx.53*
>    2. That the authorized DNS servers on the subdomain
>    midominio.principal.hosting.com are:
>    *sb1.principal.hosting.com <http://sb1.principal.hosting.com>* y el *sb2.principal.hosting.com
>    <http://sb2.principal.hosting.com>*
>
> Having said that, in my vps I have defined the following:
>
>
>
>
>
>
> *; BIND reverse data file for empty rfc1918 zone ; ; DO NOT EDIT THIS FILE
> - it is used for multiple zones. ; Instead, copy it, edit named.conf, and
> use that copy. ; *
> *$TTL 86400*
>
> *@ IN SOA sb1. sb2. mail. (*
>

The first field after "SOA" is the *ONE* master server for the  domain.
You cannot list two.  Should be:
@ IN SOA sb1. mail. (

-- 
Bob Harold


>
>
>
>
>
>
> * 10 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 86400 ) ;
> Negative Cache TTL ; REGISTROS NS sb1.*
> *principal.hosting.com <http://principal.hosting.com>. NS sb2.*
> *principal.hosting.com <http://principal.hosting.com>. IN MX 10 mail.*
> *midominio.principal.hosting.com <http://midominio.principal.hosting.com>.
> sb1 IN A *
> *xxx.xxx.xxx.52 sb2 IN A *
> *xxx.xxx.xxx.53 www IN A *
> *xxx.xxx.xxx.53 mail IN A *
>
> *xxx.xxx.xxx.53 webmail IN CNAME mail * IN A **xxx.xxx.xxx.53*
>
>
> However I can not get it to solve for example
> www.midominio.principal.hosting.com What am I doing wrong?.
> Thank you very much in advance
>
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180912/96642770/attachment-0001.html>

------------------------------

Message: 3
Date: Wed, 12 Sep 2018 19:38:51 +0200
From: Matus UHLAR - fantomas <uhlar at fantomas.sk>
To: bind-users at lists.isc.org
Subject: Re: Upgrade help with Bind 9.12
Message-ID: <20180912173851.GA11787 at fantomas.sk>
Content-Type: text/plain; charset=us-ascii; format=flowed

On 12.09.18 13:01, Spears, Luke wrote:
>I'm not sure how to go about requesting this but I am looking for information on upgrading from BIND 9.8 to 9.11 or 12 depending if it's ESV or not.  We are running Ubuntu 14.04

if you use ubuntu *-LTS, you should be safe with the version in ubuntu.

-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Honk if you love peace and quiet. 


------------------------------

Message: 4
Date: Wed, 12 Sep 2018 18:22:22 +0000
From: "BARAJAS BERMEJO, Sergio" <Sergio.BARAJAS at econocom.com>
To: "bind-users at lists.isc.org" <bind-users at lists.isc.org>
Subject: Error parsing file
Message-ID:
	<HE1PR04MB312999EAFCBC4D3064924BA6FF1B0 at HE1PR04MB3129.eurprd04.prod.outlook.com>
	
Content-Type: text/plain; charset="iso-8859-1"

Hi,

I have this zone file:


$TTL    2d
@       IN      SOA     sergiobarajas (
                             17         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                          86400 )       ; Negative Cache TTL
;
        IN      NS      ns1.hosting.com.
        IN      NS      ns2.hosting.com.
;-------- Registro MX ------------------------
                IN      MX      10      sergiobarajas.select.hosting.com.
sergiobarajas   IN      A       31.193.228.53
sb1             IN      A       31.193.228.52
sb2             IN      A       31.193.228.53

$ORIGIN sergiobarajas.select.hosting.com.
;-------Servidores de Dominio
sergiobarajas.select.hosting.com.           IN      NS      sb1.select.hosting.com.
sergiobarajas.select.hosting.com.           IN      NS      sb2.select.hosting.com.
;-------- Registro MX --------------------------
; Nombre         clase   MX      preferencia    Host
                IN      MX      10      mail.sergiobarajas.select.hosting.com.


When I do "named-checkzone select.hosting.com db.thisfile"


It outputs this error:


dns_rdata_fromtext: db.thisfile:7: near eol: unexpected end of input
zone select.hosting.com/IN: loading from master file db.thisfile failed: unexpected end of input
zone select.hosting.com/IN: not loaded due to errors.

What is wrong?

Thanks


-

Sergio Barajas Bermejo

T?cnico de sistemas


Plaza Biribila, 4, 48001 Bilbo, Bizkaia

email : sergio.barajas at econocom.com

web : www.econocom.com<http://www.econocom.com/>



[Logo_ECONOCOM_BD]


Advertencia legal: La informaci?n que figura en la presente comunicaci?n y que la acompa?a puede ser de naturaleza confidencial o bien estar sujeta a normas de confidencialidad legal o a protecciones relativas a su divulgaci?n. Tiene por ?nico objeto su utilizaci?n por parte del receptor a quien est? destinada. Si usted no es el destinatario de la presente comunicaci?n, rogamos eliminar y destruir todos los ejemplares de ?sta que se encuentren en su poder, avis?ndole al remitente que la recibi? por error. Queda expresamente prohibido examinar o difundir la presente comunicaci?n o ejecutar actos en base a la misma.

Disclaimer: The information contained in and accompanying this communication may be confidential, subject to legal privilege, or otherwise protected from disclosure, and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this communication, please delete and destroy all copies in your possession, notify the sender that you have received this communication in error, and note that any review or dissemination of, or the taking of any action in reliance on, this communication is expressly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180912/ef70b64b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-Logo_ECONO.png
Type: image/png
Size: 3209 bytes
Desc: Outlook-Logo_ECONO.png
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180912/ef70b64b/attachment.png>

------------------------------

Subject: Digest Footer

_______________________________________________
bind-users mailing list
bind-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


------------------------------

End of bind-users Digest, Vol 3004, Issue 2
*******************************************

======================================
CONFIDENTIALITY NOTICE:

This e-mail communication and any attachments may 
contain confidential and privileged information for the use 
of the designated recipients named above. If you are not 
the intended recipient, you are hereby notified that you 
have received this communication in error and that any 
review, disclosure, dissemination, distribution, or copying 
of it or its contents is prohibited. If you have received 
this communication in error, please notify the sender 
immediately and destroy all copies of this communication 
and any attachments.



More information about the bind-users mailing list