On 10/31/2011 6:58 AM, Kristen Eisenberg wrote:
Ben Croswell writes:
> In that case technically you are creating undelegated subdomains for
each
> router.
> The dot is a delimiter and can't be part of a hostname.
>
I was thinking you are wrong.
Period is somewhat permitted in a hostname.
Pe
Actually a . is not part of a host name. It separates all the parts of
FQDN. If you put one in a host name you have an undelegated subdomain as I
stated before.
-Ben Croswell
On Oct 31, 2011 6:59 AM, "Kristen Eisenberg"
wrote:
> Ben Croswell writes:
>
> > In that case technically you are creatin
On Fri, Feb 04, 2011 at 11:26:08AM -0500, John Wobus wrote:
> So 10.14.22.11 is a legal hostname, right?
>
> We had a recent experience where our DNS administration
> system allowed someone to insert in a CNAME record that
> resembled this:
>
> www.example.com. CNAME 10.14.22.11.
>
> A fascinati
So 10.14.22.11 is a legal hostname, right?
We had a recent experience where our DNS administration
system allowed someone to insert in a CNAME record that
resembled this:
www.example.com. CNAME 10.14.22.11.
A fascinating thing about this is that my computer/browser could
take me to www.example.
To add to the story, I added a rule to our DNS administration
system that we'll only allow hostnames that include
at least one alphabetic.
John
On Feb 4, 2011, at 11:26 AM, John Wobus wrote:
So 10.14.22.11 is a legal hostname, right?
We had a recent experience where our DNS administration
sys
On Sun, Jan 30, 2011 at 09:40:51AM +0800, p...@mail.nsbeta.info wrote:
> Joseph S D Yao writes:
>
> >
> > The labels must follow the rules for ARPANET host names. They must
> > start with a letter, end with a letter or digit, and have as interior
> > characters only letters, digits, and hyphen.
The rfc you quote clearly states when used as a delimiter of a domain as I
stated.
-Ben Croswell
On Jan 31, 2011 8:58 PM, wrote:
> Ben Croswell writes:
>
>> In that case technically you are creating undelegated subdomains for each
>> router.
>> The dot is a delimiter and can't be part of a hostna
In article ,
Vyto Grigaliunas wrote:
> Although we're moving away from it, we found it useful for naming router
> interfaces, i.e. te1-2.routername.company.com, without having to create a
> separate sub-domain for each router.
>
> I thought at some point periods were allowed in hostnames, and t
Ben Croswell writes:
In that case technically you are creating undelegated subdomains for each
router.
The dot is a delimiter and can't be part of a hostname.
I was thinking you are wrong.
Period is somewhat permitted in a hostname.
From RFC 952
A "name" (Net, Host, Gateway, or Do
without escaping them.
Thanks...
Vyto
-Original Message-
From: bind-users-bounces+vyto=fnal@lists.isc.org [mailto:bind-
users-bounces+vyto=fnal@lists.isc.org] On Behalf Of Barry Margolin
Sent: Sunday, January 30, 2011 4:14 PM
To: comp-protocols-dns-b...@isc.org
Subject: Re:
In that case technically you are creating undelegated subdomains for each
router.
The dot is a delimiter and can't be part of a hostname.
-Ben Croswell
On Jan 31, 2011 11:19 AM, "Vyto Grigaliunas" wrote:
___
bind-users mailing list
bind-users@lists.isc.
hanks...
Vyto
> -Original Message-
> From: bind-users-bounces+vyto=fnal@lists.isc.org [mailto:bind-
> users-bounces+vyto=fnal@lists.isc.org] On Behalf Of Barry Margolin
> Sent: Sunday, January 30, 2011 4:14 PM
> To: comp-protocols-dns-b...@isc.org
> Subject: Re: wha
On Jan 30, 2011, at 1:47 PM, Vytautas Grigaliunas wrote:
> What is the status of "dotted" hostnames - i.e. a period in the hostname
> portion of a domain name ?
>
> At one point they were allowed, I believe ? What is the latest official RFC ?
Periods, or dots, act as dividers in a domain name,
In article ,
Vytautas Grigaliunas wrote:
> What is the status of "dotted" hostnames - i.e. a period in the hostname
> portion of a domain name ?
>
> At one point they were allowed, I believe ? What is the latest official RFC ?
I don't think they've every been allowed. Why would you need to d
pm
Subject: Re: what's a valid domain name?
To: comp-protocols-dns-b...@isc.org
> In article ,
> Chris Buxton wrote:
>
> > Correct, the requirement to start with a letter was removed ages ago.
> > Witness 3com.com, which may have been the first.
>
> Yes,
In article ,
Chris Buxton wrote:
> Correct, the requirement to start with a letter was removed ages ago.
> Witness 3com.com, which may have been the first.
Yes, I'm pretty sure they were the impetus for the change, paving the
way for 1-800-FLOWERS.COM years later.
--
Barry Margolin, bar...@a
Correct, the requirement to start with a letter was removed ages ago.
Witness 3com.com, which may have been the first.
Chris Buxton
BlueCat Networks
On 1/29/11, p...@mail.nsbeta.info wrote:
> Joseph S D Yao writes:
>
>>
>> The labels must follow the rules for ARPANET host names. They must
>> s
From RFC 1123
One aspect of host name syntax is hereby changed: the
restriction on the first character is relaxed to allow either a
letter or a digit. Host software MUST support this more liberal
syntax.
p...@mail.nsbeta.info writes:
Joseph S D Yao writes:
In message <20110130013241.dff772d...@mail.nsbeta.info>, p...@mail.nsbeta.info
wri
tes:
> Mark Andrews writes:
> >
> > Remember domain names are not the same things as hostnames. Hostnames
> > are limited to letter digit hyphen (LDH). Other domain names are not
> > limited and things last SRV
Joseph S D Yao writes:
The labels must follow the rules for ARPANET host names. They must
start with a letter, end with a letter or digit, and have as interior
characters only letters, digits, and hyphen. There are also some
restrictions on the length. Labels must be 63 characters or less.
Mark Andrews writes:
Remember domain names are not the same things as hostnames. Hostnames
are limited to letter digit hyphen (LDH). Other domain names are not
limited and things last SRV records deliberately use labels that are
not legal in hostnames to prevent collisions of the two namespace
As noted before, RFC 1035 set some specifications. But there were a
number of clarifications and changes, notably RFC 1123 and RFC 2181.
So, Pyh, your quote is not quite correct today. The first part never
was - it only refers to second-level domains. The second part is
correct for hostnames on
In message <20110129053051.bad452d...@mail.nsbeta.info>, p...@mail.nsbeta.info w
rites:
> Barry Margolin writes:
>
> > In article ,
> > p...@mail.nsbeta.info wrote:
> >
> >> I googled and found this:
> >
> > It's on the Internet, so it must be true. :)
> >
> >>
> >> * A domain name
Barry Margolin writes:
In article ,
p...@mail.nsbeta.info wrote:
I googled and found this:
It's on the Internet, so it must be true. :)
* A domain name can be up to 63 characters long plus a dot plus the
characters used to identify the top-level domain (i.e "com", "info", "biz",
In article ,
p...@mail.nsbeta.info wrote:
> I googled and found this:
It's on the Internet, so it must be true. :)
>
> * A domain name can be up to 63 characters long plus a dot plus the
> characters used to identify the top-level domain (i.e "com", "info", "biz",
> etc.
> * Valid
25 matches
Mail list logo
