| |
| |
| |
|
Page: 1 2 3 4 5
Comments:
<0> can I have a non-origin domain name CNAME'd to the current zone file's domain name? in bind, that would be "foo.tld. 1D IN CNAME current.tld." ?
<1> not possible.
<1> an owner with a cname record isn't allowed anything else, and zone delegation points need at least an soa.
<0> I just created a master zone file for foo.tld with a CNAME record pointing to current.tld only but bind didn't load it
<1> naturally.
<1> please review my last statement.
<0> how can you last statement still apply when I have changed strategies?
<0> do you mean origin by owner?
<1> foo in ... ; foo is the owner
<1> if a delegation is made to foo then foo must have an soa, which precludes it also having a cname.
<0> ok I created a zone file for foo.tld with only an NS and a CNAME pointing to current.tld. there's also a currentl.tld zone file with all the necessary parameter A, NS, etc. twkm, even with this set up is it still no possible to achieve it?
<0> s/no/not/
<0> the reason for all of this is to avoid having to create a ServerAlias foo.tld for the virtualhost section of current.tld.
<1> sounds moronic.
<1> and unrelated.
<0> I'm hoping that by cnameing that domain name, http headers will be taken care of
<1> anyway, if you have a domain you cannot use cname to cause the domain to reference another domain. you must make individual entries, which can then be cname's.
<1> headers won't be changed by the client merely because of a cname.
<0> by client, do you mean browser client?
<1> that being what sends http headers, yes.
<0> what do you mean by "you must make individual entries, which can then be cname's". do you mean subdomains?
<1> www, ftp, whateverthe****else.
<0> right
<0> ok thanks
<1> foo.tld. in soa ... ; must exist, so no cname allowed for foo.tld.
<1> www.foo.tld. in cname www.other.domain.
<1> ftp.foo.tld. in cname ftp.other.domain.
<1> ..
<1> and it won't save you anyway.
<1> if the server is name-based then without a serveralias the default vhost will be used.
<0> yeah I have no control of the server on the other end. I have no idea if it's name or address based. at least, i know now that this wouldn't accomplish what I want anyway.
<0> at least I got http://www.foo.tld to p*** current.tld http headers to the web server. so http://www.foo.tld now points to http://www.current.tld. I cnamed www.foo.tld to current.tld
<2> ah got it :)
<3> I have updated my nameservers through godaddy, and it's been a while now.. but the domain is still pointing at my old host. How long should it typically take? (.com)
<1> minutes.
<1> though the old data might be cached in resovlers for as long as your previous ttl -- 1 hour to 1 week.
<3> how can I find out the ttl?
<1> if you can still see the old data then the ttl should be present too, use verbose mode of your query tool (dig uses verbose mode by default).
<1> e.g., dig your.name.here
<3> umm... dig?
<1> yes, dig is a dns query tool.
<3> i can't run it from my local windows box?
<4> hey
<1> win32 tends to come with the nslookup query tool.
<4> where to set a dns server when the main one is down
<4> and could you give me a dns server?
<1> name: your ns records describe all the nameservers that will respond for a domain.
<1> name: see the home page for a list of providers.
<4> twkm: see the home page
<4> twkm: how funny
<4> twkm: if my DNS is down
<4> the one of my provider
<1> this channel's home page you dolt.
<4> lol
<1> /topic
<4> how?
<4> it's a hostname
<3> *** triexa.com can't find nslookup: No response from server
<1> ahh, your isp provided resolver isn't working.
<4> ye
<4> exacly
<1> name: call them.
<4> twkm: nah
<4> twkm: it's 01:53
<4> twkm: just tell me how to set an alternative :_)
<1> name: just tell me what o/s and what nameserver you know of, and i'll tell you how to type what you need to type -- if you are lucky and i know what your o/s needs.
<4> linux
<1> Kaitlyn2004: i can see dreamhost as the ns' for that domain, and an a record of 208.97.129.242 which currently has a ttl of 14400 (seconds).
<1> Kaitlyn2004: are those the same nameservers as before?
<3> those were the OLD nameservers
<1> name: edit your /etc/resolv.conf file, using any text editor.
<3> i switched them..
<3> and i made then change well over an houyr ago
<3> *well hour 12 hours
<1> Kaitlyn2004: did you transfer the domain to godaddy?
<3> it was always registered on godaddy
<4> twkm: just got it ;)
<3> ahhhhh what the heck
<3> i logged in and they ARE pointing to dreamhost!?
<1> Kaitlyn2004: did you change ns records or the delegation? if the former it won't matter. if the latter i would expect a com domain to update within 15 minutes.
<4> tnx anyways
<1> Kaitlyn2004: ahh, the change didn't 'take'.
<3> why not? :S
<1> Kaitlyn2004: i cannot possibly know why.
<0> name, use /dns some.name.there
<3> it said the changes have been submitted
<1> Kaitlyn2004: try again. pay close attention to any messages produced.
<3> i got back to "set nameservers"
<4> got it
<3> and its like no change happened
<3> NOW it changed
<3> what the hell
<3> STUPID godaddy
<3> :(
<1> heh.
<3> after 3 tries of identical data
<3> lol
<3> its definitely going to change back in 5 seconds, and I want to blame dreamhost :)
<1> whois is still reporting dreamhost, but the com nameservers have ns[12].triexa.com.
<1> ahh, there, whois is updated now.
<3> that was quick
<3> what the hell
<3> lol
<3> hmm
<3> when i do a tracert, ip is still dreamhost's, and it ends at dreamhost
<3> how do you have urs updated so quickly?
<1> whois isn't cached -- at least mine isn't. and for dns i checked with the com zone directly, my local dns resolver still thinks your ns' are at dreamhost (and will continue to think it for 14266 seconds).
<3> i seeeeee
<3> so basically it won't change for AT LEAST almosst 5 mintues?
<3> oh wait..
<3> 3 hours?
<1> well, 14400 seconds is 4 hours.
<3> right..
<1> so i've got 3+ hours to go.
<3> as do I, right?
<1> right.
<3> darn :( haha
<3> alright thanksss!
<1> cool.
<3> huge help you are! :)
<1> easy peasy -- just bash godaddy's interface a few times.
<3> haha and guess what? My e-mail contained 3 notification e-mails for changing to nameservers too
<3> lol
<3> is a ttl of 4 hours "standard"
<3> ?
<1> it is not too odd.
<1> most people don't change things too often.
<4> hum
<4> is that possible
<4> only some adresses resolv
<3> me again:) so how did you exactly find out the value of the TTL?
<1> i used dig ... ''dig trixea.com ns''
<1> dig for win32 is available from http://ftp.isc.org/isc/bind/contrib/ntbind-9.3.2/BIND9.3.2.zip
<3> hmm
<3> ;; global options: printcmd
<3> ;; connection timed out; no servers could be reached
<1> odd.
<3> boo lol
<1> sorry. i admit i haven't used it on win32 in a while, but last time i did it worked.
<3> i see
<3> alright
<3> i did it from my other server
<3> i don't see anything saying TTL though?
<3> oops
<3> guessing its 12842
<3> or 14333?
<1> yes, that number.
<3> :)
<3> finally. hjaha
<3> just to feed my curiosity :)
Return to
#dns
or
Go to some related
logs:
create table script mysql -php
#php
#lisp
iptables -s ipgroup
#math
php mysql list databases order by
ppc etch glxgears
fedora ivasquez
#php
#perl
|
|