On 06/15/2012 04:43 PM, Mateusz Marzantowicz wrote:
> Yes, every nonexistent domain name is evaluated to . domain> which then resolves to my public IP (it is a wildcard dns record
> in action I think). That explains why domain name with trailing dot
> wasn't glued with my domain (two dots in FQDN a
On 15.06.2012 10:20, Ed Greshko wrote:
> On 06/15/2012 03:54 PM, Mateusz Marzantowicz wrote:
>> Thanks for your interest. I'm confused more and more now.
>>
>> I've installed Wireshark to see what's going on behind the scene and
>> here is a brief info of DNS related packets:
>>
>> 1) My IP -> rout
On 06/15/2012 03:54 PM, Mateusz Marzantowicz wrote:
> Thanks for your interest. I'm confused more and more now.
>
> I've installed Wireshark to see what's going on behind the scene and
> here is a brief info of DNS related packets:
>
> 1) My IP -> router: standard query A
> 2) router -> My IP: sta
On 15.06.2012 03:59, Ed Greshko wrote:
> On 06/15/2012 08:05 AM, Mateusz Marzantowicz wrote:
>> Nothings changed. I'm pretty much sure right now that some app or script
>> is silently messing with resolvers configuration. It's exactly the
>> behavior of /etc/resolve.conf with search opt configured
On 06/15/2012 08:05 AM, Mateusz Marzantowicz wrote:
> Nothings changed. I'm pretty much sure right now that some app or script
> is silently messing with resolvers configuration. It's exactly the
> behavior of /etc/resolve.conf with search opt configured but I have only
> single line there!
Well,
On 15.06.2012 01:19, Ed Greshko wrote:
> On 06/15/2012 06:56 AM, Mateusz Marzantowicz wrote:
>> $ ping furdishcamp.com
>> PING furdishcamp.my.domain.here (x.y.z.9) 56(84) bytes of data.
>>
>>
>> This happens with Firefox too which is the most annoying for me because
>> I drop to my personal web ser
On 06/15/2012 06:56 AM, Mateusz Marzantowicz wrote:
> $ ping furdishcamp.com
> PING furdishcamp.my.domain.here (x.y.z.9) 56(84) bytes of data.
>
>
> This happens with Firefox too which is the most annoying for me because
> I drop to my personal web server every time the domain is not found. I'd
> p
On 15.06.2012 00:37, Ed Greshko wrote:
> On 06/15/2012 05:45 AM, Mateusz Marzantowicz wrote:
>> I have noticed a strange (for me) behavior of dns resolver in Fedora 17.
>> If the domain name being resolved simply doesn't exists I'm provided
>> with my IP address instead of an error. It behaves like
On 06/15/2012 05:45 AM, Mateusz Marzantowicz wrote:
> I have noticed a strange (for me) behavior of dns resolver in Fedora 17.
> If the domain name being resolved simply doesn't exists I'm provided
> with my IP address instead of an error. It behaves like when the search
> option is present in /etc
I have noticed a strange (for me) behavior of dns resolver in Fedora 17.
If the domain name being resolved simply doesn't exists I'm provided
with my IP address instead of an error. It behaves like when the search
option is present in /etc/resolv.conf but it isn't. I suspect that it
was added by so
10 matches
Mail list logo
