Hello all,
my problem is quite simple, but I've tried a lot of different setups,
none worked :(
My company's DNS are hosted by an third-operator. In the zone
"websiteburo.com", there are several A records, pointing on our
different servers.
My problem is: a few of these servers are hosted lo
Someone correct me if I'm wrong but using BIND you must have the full
zone, partial forwarding/proxying isn't built in so you would need to
download the zone and replace the data you need to change.
/Jonathan
On Fri, Nov 13, 2009 at 11:22 AM, Johan VAN RYSEGHEM
wrote:
> Hello all,
>
> my problem
Ok, i solved my problem using pdnsd
(http://www.phys.uu.nl/~rombouts/pdnsd/doc.html). Seems it fits my needs
better.
Tanks for your help
Johan
Jonathan Petersson a écrit :
Someone correct me if I'm wrong but using BIND you must have the full
zone, partial forwarding/proxying isn't built in
On 11/13/2009 6:44 AM, Jonathan Petersson wrote:
Someone correct me if I'm wrong but using BIND you must have the full
zone, partial forwarding/proxying isn't built in so you would need to
download the zone and replace the data you need to change.
If all you want to do is change an A record (s
Hello !
I have a little problem :
We have 4 little datacenters over the world.
I would like to check if all DNS servers are up to date but only people
responsible of a datacenter can access their servers for security reasons.
I know some tools on the net can do that but it's not easy for me and
Thomas Harold a écrit :
On 11/13/2009 6:44 AM, Jonathan Petersson wrote:
Someone correct me if I'm wrong but using BIND you must have the full
zone, partial forwarding/proxying isn't built in so you would need to
download the zone and replace the data you need to change.
If all you want to do
Tibo a écrit :
Hello !
I have a little problem :
We have 4 little datacenters over the world.
I would like to check if all DNS servers are up to date but only people
responsible of a datacenter can access their servers for security reasons.
I know some tools on the net can do that but it's not
you can always try:
dig @dns.server.to.query version.bind chaos txt
which would return something like:
;; QUESTION SECTION:
;version.bind. CH TXT
;; ANSWER SECTION:
version.bind. 0 CH TXT "djbdns 1.05"
(sorry for the djbdns
On 11/13/2009 9:39 AM, Johan VAN RYSEGHEM wrote:
I thought I tried this. I retried and guess what, it worked. Seems like
my original setup was wrong. I must have misused the $ORIGIN keyword.
Nonetheless, I think i'm going to keep pdnsd, as it's easier to setup
for the my use.
And just for compl
Hello,
You can ask them to run this:
dig -t txt -c chaos VERSION.BIND @
or my be you are lucky and this web is usefull for you:
http://www.howismydns.com/tools.php
good luck.
Joan Marc Riera Duocastella
Barcelona Media - Centre d'Innovació
Av. Diagonal, 177, planta 9 08018 - BARCELONA
Tel
Leonardo Rodrigues a écrit :
Tibo escreveu:
I think I found it : fpdns -f NAMESERVER
Is it always OK ?
No, that's not always OK, because -f option of fpdns relies on the
version.bind record, which i explained on my previous message that
sometimes cant be queries and other times can fake
Tibo escreveu:
I think I found it : fpdns -f NAMESERVER
Is it always OK ?
No, that's not always OK, because -f option of fpdns relies on the
version.bind record, which i explained on my previous message that
sometimes cant be queries and other times can fake some false version id.
fpdn
Tibo said:
> Leonardo Rodrigues a écrit :
> > Tibo escreveu:
> >>
> >> I think I found it : fpdns -f NAMESERVER
> >>
> >> Is it always OK ?
> >
> >No, that's not always OK, because -f option of fpdns relies on the
> > version.bind record, which i explained on my previous message that
> > s
13 matches
Mail list logo
