In message <20160718141147.ga16...@fantomas.sk>, Matus UHLAR - fantomas writes:
> On 18.07.16 13:59, Harshith Mulky wrote:
> >I had a query on how the following Records can be ordered on how the Records
> >are configured in the
> Zone file
> >
> >I have done 2 different Tests
> >
> >I have
Oscar,
On point 4 there,
At this time franklin.jetbbs.com ONLY RESOLVES TO 104.238.117.105
The way I wanted it was 104.238.117.105 AND 132.148.11.44to point to
jetbbs.com but I think I setup the DNS record wrong. I just added
another A record for jetbbs.com and added the IP address
Negative Ghostrider...:
[root@foo:~]# iptables -t raw -nvL
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
I don't think my earlier response to this has made it past moderation, but
an update:
iptables looks pretty benign to me...:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywherestate
RELATED,ESTABLISHED
In article ,
Ian Veach wrote:
> So unless I'm crazy (possible, regardless)... named is reporting using 230,
> but OS is showing 240 (and remote host logs confirm 240)!?
Could something in iptables be transforming
Der, sorry. Machines are all RHEL 6.8, running the BIND provided by RH:
9.8.2rc1-RedHat-9.8.2-0.47.rc1.el6
Restarting BIND (or even the OS) doesn't seem to change anything. I don't
seem to have scan as an option for rndc. I assume it's in a newer version
that RH doesn't yet provide for RHEL 6.
Ian Veach wrote:
>
> So, any ideas on why I would see that slave initiate transfers on it's OS
> IP versus the transfer-source IP... especially when the other three work
> fine?
What does the log say about interface addresses? Which version of BIND are
you running? Has
I'm having a weird problem where one of our DNS servers is not
communicating on the expected transfer-source IPs (but the rest are).
They're generally configured exact/similar, but there's obviously something
causing a difference on the one node.
We run four slave DNS as public NS (with private
On Sun, 17 Jul 2016, Spork Schivago wrote:
> So, in the /var/named directory, I create a file
> called: 0.117.238.104.in-addr.arpa
>
> The contents of 0.117.238.104.in-addr.arpa are as follows:
> $TTL 1D
> @ IN SOA ns1.jetbbs.com. spork.jetbbs.com. (
>
Thanks Tony for your answer,
and is there any possibility using other category and/or debug level to
obtain the record and the ip resolved in the same log entry?
Regards
Manuel
2016-07-18 12:50 GMT+02:00 Tony Finch :
> Manuel Ramírez wrote:
> >
> >
On 18.07.16 13:59, Harshith Mulky wrote:
I had a query on how the following Records can be ordered on how the Records
are configured in the Zone file
I have done 2 different Tests
I have configured following records in the Zone file e164enum.net with TTL
value as 0
Hello Experts,
I had a query on how the following Records can be ordered on how the Records
are configured in the Zone file
I have done 2 different Tests
I have configured following records in the Zone file e164enum.net with TTL
value as 0
2.7.5.2.7.9.2.5.3.1.8.e164enum.net. IN NAPTR 100 10
I haven't done it with GoDaddy but many providers WILL delegate reverse IPs to
you if you request it.
Personal editorial comment:
Were it me I wouldn't use GoDaddy for anything. I detest GoDaddy because
their whole business model seems aimed at forcing you to leap through hoops to
do
Am 18.07.2016 um 12:48 schrieb Tony Finch:
> If your rollover time is much shorter then you are testing something that
> is more like an emergency unplanned rollover.
At the moment I am merely testing in this "high-frequency" setup to get
a good feeling for the mechanics and the interaction
Manuel Ramírez wrote:
>
> I would like to know if is possible to see in the queries.log output the ip
> address resolved
No, it only logs the query not the answers.
Have a look at passive DNS or dnstap if you want more detailed telemetry.
Tony.
--
Nis Wechselberg wrote:
> Am I getting it right that the rest of the zone is not (re)signed
> because the current signature is still valid for some time?
>
> So if I were to set sig-validity-interval to a shorter value, this would
> help with the issue?
If you are testing out a
Hi,
first of all sorry for my poor English.
I would like to know if is possible to see in the queries.log output the ip
address resolved, for example, this is one line from the queries.log:
*18-Jul-2016 10:54:15.226 queries: info: client 10.1.116.27#10760
(update.microsoft.com
17 matches
Mail list logo