I know you said, "Never mind," but you seem to be misunderstanding
something here ...
On Tue, Sep 09, 2014 at 07:42:56PM -0600, LuKreme wrote:
> # named-checkconf -z | grep -v loaded
> master/bt.tld:3: ignoring out-of-zone data (bt.tld)
> master/bt.tld:15: ignoring out-of-zone data (webdav.bt.tld
> Hi,
>
> xxx.com and IP address 192.168.1.100 is just a example domain name and IP
> address. Our boss want everybody access our domain example.com through
> browser, then it will redirect to our web site www.example.com. So I want
> to get more information about unexpected impact when we changed
In article ,
sch...@adi.com (Thomas Schulz) wrote:
> > Hi,
> >
> > xxx.com and IP address 192.168.1.100 is just a example domain name and IP
> > address. Our boss want everybody access our domain example.com through
> > browser, then it will redirect to our web site www.example.com. So I want
>
On 9/10/14, 8:42 AM, Sam Wilson wrote:
> And you could reduce maintenance very slightly by replacing
>
> www in A 75.100.245.133
>
> with
>
> www in CNAME @
And now you have an MX record, 3 NS records and a bunch of other crap
associated with the WWW
On 9/10/14, 8:42 AM, Sam Wilson wrote:
And you could reduce maintenance very slightly by replacing
www in A 75.100.245.133
with
www in CNAME @
On 10.09.14 08:58, Alan Clegg wrote:
And now you have an MX record, 3 NS records and a bunch of other crap
On 9/10/2014 11:58 AM, Alan Clegg wrote:
On 9/10/14, 8:42 AM, Sam Wilson wrote:
And you could reduce maintenance very slightly by replacing
www in A 75.100.245.133
with
www in CNAME @
And now you have an MX record, 3 NS records and a bunch of other
On 9/10/14, 2:13 PM, Kevin Darcy wrote:
> On 9/10/2014 11:58 AM, Alan Clegg wrote:
>> On 9/10/14, 8:42 AM, Sam Wilson wrote:
>>
>>> And you could reduce maintenance very slightly by replacing
>>>
>>> www in A 75.100.245.133
>>>
>>> with
>>>
>>> www in CNAME
On 9/10/2014 5:20 PM, Alan Clegg wrote:
On 9/10/14, 2:13 PM, Kevin Darcy wrote:
On 9/10/2014 11:58 AM, Alan Clegg wrote:
On 9/10/14, 8:42 AM, Sam Wilson wrote:
And you could reduce maintenance very slightly by replacing
www in A 75.100.245.133
with
www in
Hey Kevin,
This is not an issue at all.
A PTR is different then a "A" record and can be used by two reverse
domain names and only the owner of the IP addresses space can define them.
I am not sure if two PTR records for two domains will be applied to one
IP but it is possible for two IP address
No, what I'm saying is that if
example.com owns an A record 203.0.113.48, and
www.example.com owns an A record 203.0.113.48, then
where does 48.113.0.203.in-addr.arpa point?
Some people will point it at example.com, some will point it at
www.example.com. What you get is a mish-mosh. No consist
Well this is a confusing point but it's rather an administrative
decision to make.
If indeed the network\server\domain administrator is not aware of his
services he will either have or will not have decision to make.
It will depend on whether he knows what he is doing.
Mish-mosh or banana he wil
11 matches
Mail list logo
